{\rtf1\mac\ansicpg10000\cocoartf824\cocoasubrtf410
{\fonttbl\f0\fnil\fcharset77 LucidaGrande;\f1\fswiss\fcharset77 Helvetica;}
{\colortbl;\red255\green255\blue255;}
\margl1440\margr1440\vieww13560\viewh13260\viewkind0
\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\ql\qnatural

\f0\fs22 \cf0 Amarok is a featureful music player for KDE.\
\
This package supports Mac OS X 10.4 (PowerPC and Intel) and is automatically generated from the snapshots created by the Mac OS X dashboard build ({\field{\*\fldinst{HYPERLINK "http://public.kitware.com/dashboard.php?name=kde"}}{\fldrslt 
\f1\fs24 http://public.kitware.com/dashboard.php?name=kde}}
\f1\fs24 ).
\f0\fs22 \
\
How to report\
------------\
Reporting bugs is an art. Why?  Because bug reports can help and hinder.\
\
They hinder if the developers are just buried in an avalanche of bug reports.  They spend hours figuring out which bug reports are valid and which aren't, which bug reports are due to bugs or due to installation problems.\
\
They can be of tremendous help to notify developers on problems in areas that they normally don't have access (e.g. KDE on AIX) to.\
\
So, here are some tips on bug reporting:\
\
* Make sure your bug is due to KDE ... and not due to a packaging problem of your OS distributor. For example, most "I can not install the XYZ.rpm" problem are due to packaging issues. Refer with such questions to your OS Distributor and his appropriate mailing list or bug reporting tool.\
\
* The chance is high that your bug has already been dealt with ... so look if there is a newer version of kdelibs available. Reporting bugs for older, deprecated versions usually don't get that much attention :-)\
\
* Also the chance is high that another one experienced your problem. The bug report wizard at {\field{\*\fldinst{HYPERLINK "http://bugs.kde.org/"}}{\fldrslt http://bugs.kde.org/}} will help you to find out if your problem has already been reported.\
\
* KDE Applications come with a Report Bug option in the Help menu that will fill out many of the forms on the bug reporter tool at {\field{\*\fldinst{HYPERLINK "http://bugs.kde.org/"}}{\fldrslt http://bugs.kde.org/}} for you.\
\
* The best bug report for a project based on voluntary work is of course one that comes with a patch that solves the problem. :-)\
\
\
More info\
--------\
\
{\field{\*\fldinst{HYPERLINK "http://www.kde.org/"}}{\fldrslt http://www.kde.org/}} is a good starting point for info on KDE. If you are a developer, you may also point your browser to {\field{\*\fldinst{HYPERLINK "http://developer.kde.org/"}}{\fldrslt http://developer.kde.org/}}.  There is a plethora of mailing lists available, you can gain an overview quickly by looking at {\field{\*\fldinst{HYPERLINK "http://lists.kde.org/"}}{\fldrslt http://lists.kde.org/}}.\
\
General discussion should go to the KDE mailing list ({\field{\*\fldinst{HYPERLINK "mailto:kde@kde.org"}}{\fldrslt kde@kde.org}}).}